Upgrading time-machine to version 3.x requires fixing test that mocks the monotonic using time_machine.shift.

Since version 3.0.0, time-machine doesn't mock time.monotonic (see release notes). So, test_stream_build_logs_retry_timeout tests started to fail.
I fixed it in 1109caa.

There are 3 more tests that are somehow related to logic that uses monotonic:

• test_fetch_access_token_uses_default_timeout - already uses patch with side_effect - no changes needed
• test_short_wait_messages - mocked monotonic incorrectly
• test_long_wait_messages - mocked monotonic incorrectly

test_short_wait_messages and test_long_wait_messages didn't fail because they didn't actually tested what they claimed (didn't test that expected "long wait" or "short wait" messages appear in output).
So, I updated these 2 tests to actually test that arrays with messages are accessed (see commit 6ea3ee8), and then test_long_wait_messages test started to fail (as expected).
I fixed the way these tests mock monotonic as well in commits 37781be and 85c3b80